
Conner Backup Exec, Version 2.1.2


Copyright Arcada Software, Inc. 1995.


This file contains important technical information about
your program.

To print this file, type COPY README.TXT PRN at the DOS
prompt.

The following subjects are discussed:

   1.  Installation
   2.  Memory Requirements
   3.  Verify Your First Backup
   4.  Tape Despooling
   5.  Compatibility Test Failure
   6.  Running Conner Backup Exec under DesqView
   7.  Compressed Drives
   8.  Installing Conner Backup Exec on a System with Stacker
   9.  The DOS Append Command
  10.  Setup File Compatibility with Conner Backup Exec for Windows
  11.  Hardware Compression Not Supported
  12.  Power Management Conflicts
  13.  Parallel Port Drive Configuration
  14.  IRQ Conflicts
  15.  Maximum Parallel Port Cable Length
  16.  Potential Conflict with PC-DOS 6.1 RAMBOOST
  17.  Encrypted Backup Sets
  18.  Backing Up Large Numbers of Files to AccuTrak Tapes
  19.  NetWare Server Information and AccuTrak Tapes
  20.  NetWare Files With an Execute Only (X) Attribute
  21.  Files Not Backed Up
  22.  Formatting Tapes on 386 Machines
  23.  Tape Format Incompatibilities
  24.  3020 Drive Requirements
  25.  Controller Conflicts


   1.  Installation


Conner Backup Exec for DOS will not install or operate correctly
from a DOS box within Windows. It must be installed and operated
directly from the DOS prompt.

This program works best when both the BUFFERS and FILES statements
in your CONFIG.SYS file are set to at least 30. This program must
have a FILES setting of at least 10 and a BUFFERS setting of at
least 15 to run efficiently.

NOTE: If you are using other software that requires a lower buffers
setting, you should manually adjust the buffers setting.



   2.  Memory Requirements


Conner Backup Exec for DOS requires at least 512K of free memory;
however, this software runs faster if more memory is
available. To check your free memory, type MEM at the
MS-DOS prompt. To free memory, remove any TSRs before
running Conner Backup Exec. See your system documentation for other
methods.



   3.  Verify Your First Backup


When you make your first backup with Conner Backup Exec, it
is highly recommended that you use the Read and Compare
option. During the Compare phase, Conner Backup Exec compares
each file on the tape with the original on your hard drive to
ensure that they are identical. While comparing will increase
the time of the backup, it will confirm that your computer
system, tape drive, and Conner Backup Exec are working
together correctly. If compare fails, run a hard disk utility
program to determine whether the hard drive is free of errors
and try the backup again.



   4.  Tape Despooling


If a tape "despools" (comes loose from the cartridge capstan,
a very rare occurrence), it may be necessary to turn the drive's
power off and on again or to reboot your system to clear the
drive.



   5.  Compatibility Test Failure


The compatibility test consists of a small backup and
compare, automatically performed by Conner Backup Exec to verify
that reliable backups can be performed with your current
configuration.

The most common cause of compatibility test failure is DMA
error. Therefore, when the compatibility test fails,
Conner Backup Exec automatically resets the DMA
(Direct Memory Access) to Low Speed.

During installation, other factors may contribute to
compatibility test failure. For this reason, the following
procedure is recommended if the compatibility test fails
during installation:

    1. Complete the installation
    2. Restart Conner Backup Exec
    3. Choose Configure
    4. Choose Configuration Tests
    5. Set the Direct Memory Access to High Speed
    6. Redo the compatibility test

If the compatibility test fails again, follow the guidelines
presented in the on-line help, available by pressing F1.



   6.  Running Conner Backup Exec under DesqView


To run Conner Backup Exec under DesqView, make the following
selections in DesqView:

    Create an entry in the Program Menu for Conner Backup Exec.

    Under Advanced Options, specify that Conner Backup Exec
     cannot share CPU when in the foreground, and that
     it cannot run in the background.

    Select Uses Its Own Colors.

    Set the Memory Size option to 512 K.



   7.  Compressed Drives


If you are using compression software such as Stacker or
DoubleSpace, do not back up the compressed file, back up the
logical drive instead. Because these compressed files are
typically very large, attempting to restore may cause problems
if you do not have enough disk space to restore the compressed file.



   8.  Installing Conner Backup Exec on a System with Stacker


If you have Stacker software installed on your computer,
you may not want to let Conner Backup Exec make changes to your
AUTOEXEC.BAT file. Some versions of Stacker create their
own AUTOEXEC.BAT file which should not be modified, and it
is this file that Conner Backup Exec will find.

You can tell if this is the case on your computer if, during
Conner Backup Exec installation, the AUTOEXEC.BAT file that is
displayed says "DO NOT MODIFY THIS FILE." In this case, you
will need to find your original AUTOEXEC.BAT file and make
the following changes:

  Add the Conner Backup Exec directory to your PATH statement.

  Add the command "SET QBACKUP=path_name"

      where path_name is the directory you want Conner Backup Exec
      to use for setup and catalog files

  If you want to load the Backup Scheduler each time you
   start your computer, add the command QSCHED as the last
   command in your AUTOEXEC.BAT file.

For more information on loading the Backup Scheduler, see the
help topic "Installing the Backup Scheduler TSR."



   9.  The DOS Append Command


If you use the DOS Append command with the /X or /X:ON
option, when you perform a restore, some files may not be
restored.  This is because of the way DOS reports names of
existing files when this command is in effect.

It is highly recommended that you deactivate the Append /x
command before performing restores.



  10.  Setup File Compatibility with Conner Backup Exec for Windows


Conner Backup Exec for Windows, version 2.1.2, can read, use,
and modify setup files created by Conner Backup Exec for DOS,
version 2.1.2. If you have made individual file or directory
selections in a setup file that is opened and resaved by
Conner Backup Exec for Windows, you may notice that some
filenames and directory names are displayed in a different
color (red if default colors are used). This display change
will not affect the selections.

Conner Backup Exec for DOS, version 2.1.2, can use setup files
created by Conner Backup Exec for Windows, version 2.1.2,
with the following limitation:

    Individual file and/or directory selections made with
    the keyboard or mouse will not transfer from the Windows
    setup file to the DOS setup file.



  11.  Hardware Compression Not Supported


Conner Backup Exec for DOS, Version 2.1.2, does not support
the hardware compression function found on some high-speed
controller cards.



  12.  Power Management Conflicts


Some Desktop computer systems and laptops have power
management systems that take a "snapshot" of RAM and
store it on the hard drive when they power down. This
may create a conflict if it occurs during a backup or
restore or a tape formatting operation.

When using Conner Backup Exec, it is recommended that you turn
OFF all power management features. If you're using
a laptop, avoid running power management features
by using an outlet rather than batteries.



  13.  Parallel Port Drive Configuration


If your parallel port tape drive does not automatically
configure, first ensure that the power to the drive is on. If
it is, turn it off, then on, and try configuring it again. See
below for more suggestions.



  14.  IRQ Conflicts


You may experience a conflict in IRQ selection if you are
configuring a parallel port tape drive on a system that
includes a sound card. SoundBlaster cards and compatibles use a
default IRQ of 7, which is also used by a printer port (LPT1).
If this conflict occurs, you can:

    *  Change your sound card's IRQ if possible. Some cards do
       not allow this change and some games may not work
       correctly.

    *  Check your system documentation to see if your parallel port
       can be configured to use a different interrupt.

Devices that may conflict with printer port interrupt:

       Sound Cards
       Scanner Cards
       Network Cards
       Bus Mice
       Other printer ports
       Other devices

IRQ usage can be determined by using the Microsoft Diagnostics
Program. Exit Windows and type MSD at the DOS prompt. Note that MSD
cannot always diagnose printer port IRQ conflicts. Printing does not
require a hardware interrupt and will function normally even if an
interrupt conflict exists.

Symptoms of an IRQ conflict include Conner Backup Exec not
finding the tape controller and network problems when
backing up to tape.



  15.  Maximum Parallel Port Cable Length


Your parallel port tape drive should be connected directly to
your system's parallel port. If you use the pass-through
connector on the drive to connect a second device such as a
printer, the maximum cable length for both devices is
approximately 10 feet (3 meters).

If you have difficulty using your tape drive when a second
device is connected to the pass-through connector, disconnect
the second device and its cable while using the tape drive.

If you experience data loss when using a printer connected to
the pass-through connector, shorten the printer's cable if
possible or disconnect the tape drive while printing.



  16.  Potential Conflict with PC-DOS 6.1 RAMBOOST


If you wish to use the Scheduler TSR, QSCHED.COM, with PC-DOS
6.1's RAMBOOST device, you must use the /SKIPHIGH switch to load
it in conventional memory. Type QSCHED.COM /SKIPHIGH at the
command line or include it in your AUTOEXEC.BAT line. NOTE: The
QSCHED.COM TSR must be loaded last.



  17.  Encrypted Backup Sets


Conner Backup Exec cannot restore backup sets encrypted by
other backup programs. You must use the original software to
restore them.



  18.  Backing Up Large Numbers of Files to AccuTrak Tapes


When using AccuTrak tapes, backing up a very large number of
files--approximately 30,000 to an 80MB tape or 45,000 to a
120MB tape--will result in an error. Divide the files into
two or more backup sets and back up each set to its own tape.



  19.  NetWare Server Information and AccuTrak Tapes


Because of the proprietary format used by the tapes, NetWare
bindery files, trustee information, and extended attributes
cannot be backed up to AccuTrak tapes.



  20.  NetWare Files With an Execute Only (X) Attribute


NetWare files with an execute only (X) attribute will not be
backed up, compared, or overwritten during a restore.



  21.  Files Not Backed Up


Conner Backup Exec does not log or back up a number of files
to avoid potential system conflicts if they are restored.

  Compressed Volume files:

     DBLSPACE.0??
     DRVSPACE.0??
     STACVOL.*

  Windows swap files:

     386SPART.PAR
     WIN386.SWP

  NetWare System files:

     BACKOUT.TTS
     NET$SPL.QUE
     NET$MSG.SYS
     DIRSTAMP.SYS
     NET$OBJ.SYS*
     NET$PROP.SYS*
     NET$VAL.SYS*
     NET$BIND.SYS*
     NET$BVAL.SYS*
     SYS$LOG.ERR

 * These NetWare bindery files will be backed up or restored
   only if you are logged on to a server as Supervisor. See your
   User Guide for more information.

Additionally, Conner Backup Exec will not back up a number of
temporary files used by the program when these files are found
in the program's directory.



  22.  Formatting Tapes on 386 Machines


If you encounter difficulties formatting tapes on a slower 386
machine or receive a message stating "The tape controller is not
responding correctly," make sure your turbo switch is on.



  23.  Tape Format Incompatibilities


Conner Backup Exec cannot format AccuTrak tapes. If
your drive supports AccuTrak tapes, you should purchase them
preformatted.



  24.  3020 Drive Requirements


To achieve optimal performance with a 3020 drive, a 1Mbit
controller or higher (2Mbit) is required.



  25.  Controller Conflicts


The Promise 2300 EIDE VLB controller must run in fast
mode (/f parameter) in order to work with floppy tape drives.


